This PR is a, reworked, part of the larger PR #1204

This changes optimize the serialization for common geometry types in SQL/MM (like CURVEPOLYGON, CIRCULARSTRING, etc.).
It also extends the linearization code to allow SQL/MM like circles which are defined through the points of the diameter.
This change extends the current code which implements the GML 3.x way of circles, which would be incompatible, to also allow circles like in SQL/MM.

Quote from the GML 3.2 specification

A Circle is an arc whose ends coincide to form a simple closed loop. The three control points shall be distinct non-co-linear points for the circle to be unambiguously defined. The arc is simply extended past the third control point until the first control point is encountered.

Quote from the PostGIS documentation (SQL/MM Part 3)

CircularString is the basic curve type, similar to a LineString in the linear world. A single arc segment is specified by three points: the start and end points (first and third) and some other point on the arc. To specify a closed circle the start and end points are the same and the middle point is the opposite point on the circle diameter (which is the center of the arc). In a sequence of arcs the end point of the previous arc is the start point of the next arc, just like the segments of a LineString. This means that a CircularString must have an odd number of points greater than 1.